Conversation
During flywork setup, Maven caches failed remote lookups in .lastUpdated files. When building repos sequentially by DAG layer, artifacts installed locally by a previous layer can be missed because Maven serves the cached failure instead of rechecking. The -U flag forces Maven to ignore these caches and always re-resolve, fixing first-pass build failures.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--jsonflag is set to prevent corrupting JSON output parsed by the DAG orchestrator-Uflag to Maven install commands to force re-resolution of cached failures duringflywork setupTest plan
go vet ./...passesgo buildsucceedsflywork dag export --json | jq .outputs clean JSON (no banner)flywork setup --freshcompletes without first-pass dependency failures